OK, so throughout this entire.
Tutorial lessons, we've discussed them pretty much as a standard text based editor, but you can actually
use it within Visual Studio Code, you can use them key bindings and VIMS settings.
You can use it within visual studio code.
So if you're switching between like a Linux or, you know, just using them and you say, for instance,
you're moving to a place that uses visual studio code as their primary editor, or you just want to
look at how you can integrate them within Visual Studio code, you can do that by using one of the many
vim extensions that are out there.
Now, this one right here, I actually have installed as Code Vim and essentially what this does, it
allows me to have them within visual studio code, but it's slightly different.
Well, actually, it's not even just slightly different.
It is different essentially because you don't have a democracy file.
You have a settings that Jason file that you use to essentially coordinate your key bindings to your
Vim installation within Visual Studio code.
So essentially, you'll have to find your edit right here.
Command line mode, key bindings here.
You have to edit your settings that Jason file.
And I'm going to include a very basic version of a settings that Jason file for the VM extension.
And, you know, essentially it will act very similar to some of the key bindings I've set up in them
prior to this course.
So.
The thing of it is, is with whenever you're customizing them, it's a highly personal thing, so what
settings you choose to use and how you choose to customize it is really dependent upon your personal
choice.
So that means that, OK, what I use is something that maybe you don't want to use.
So while I'm including the example file, you may find it difficult to use, in which case, then I
encourage you to go out and research it some more and find you basically go and try to fix it so that
it's exactly how you like it.
So you can do the same thing.
Actually, with this niobium extension, it works very similar to the vim emulation as it would for
the neerim except Neerim.
I haven't don't have it installed.
But what it actually does is it looks for a VM that it looks for the innot that VM file and you can
basically say within your own, for instance, you have Novem on windows.
It will look for the you know, if it exists, there's code within your file.
So by using the neerim installation or version of it, you can switch between new of them on the command
line, the command prompt and which is code, and it will essentially be the same settings.
So using them or the nerem extension is really entirely up to you.
As I say, you can really get into it.
There are plenty of example settings or Jason files on GitHub and on the Internet that you can look
and then see how you want to modify it.
Again, it's highly personal.
Would I recommend you used any of them extension?
Sure you could.
You can use the Vim extension.
Many people that I know are switching to the niobium extension and I'm seriously considering it myself.
So that's maybe the way you want to go.
And as you can see, that it's pretty well documented here on exactly how you can use this.
And if you see here, it's as if it exists, you know, with VNS code and you would use the V as code,
otherwise you would just use your standard ordinary knew of in a particular setting.
So as you can see, you can use them or any of them within Visual Studio Code.
And that actually creates a big advantages because then you can switch between the two so that you can
essentially speed up your workflow, you can use them on the command line or you could use them within
visual studio code.
It's entirely up to you.